the plan
#projects
I'm taking this project also as opportunity to learn more and expend my knowledge worst case scenario we get cool models, documentation and plus we learn more cool stuff
the plan is to scan the one part we have scan the area of assembly on the car, using softer refine it and make it to 3d model, send it either to 3d print or to laser cutting and welding
3d printing is easier but also cheaper and look way worst then 3d metal part by laser: this is way we using the 3d model to make 2 parts; one for 3d print and one for metal fabrication
Day | Time | Task |
---|---|---|
Day 1 | 16:00 - 17:00 | Preparation (cleaning the part) |
17:00 - 19:00 | Scanning the part | |
19:00 - 20:00 | Post-processing scan data | |
Day 2 | 16:00 - 17:00 | Import scan data into CAD software |
17:00 - 20:00 | Begin modeling the part | |
Day 3 | 16:00 - 20:00 | Continue modeling the part |
Day 4 | 16:00 - 20:00 | Finalize the model |
Day 5 | 16:00 - 17:00 | Export the model as an STL file |
17:00 - 20:00 | Slice the model and generate G-code | |
Day 6 | 16:00 - 17:00 | Set up the 3D printer |
17:00 - 21:00 | Start and monitor the print job | |
Day 7 | 16:00 - 20:00 | Continue printing (if needed) |
20:00 - 21:00 | Post-processing the printed part | |
Day 8 | 16:00 - 17:00 | Inspect the printed part |
17:00 - 20:00 | Fix any issues and make adjustments | |
20:00 - 21:00 | Reprint if necessary |
3d modeling - blender
for scan review and pipelining
3d scanning - meshroom
free, opensource software for 3d scanning using camera
https://github.com/alicevision/Meshroom?tab=readme-ov-file
3d printing -
cad - onshape
easy, free, cad software for basic work and planing
i know that the 3d scanning we use here is not perfect definitely not for the cad work we do, but it will allow us to make the progress way fester, focusing and the difficult part like modeling holes and precise shape and aligning the models.
plus i might the chance to 3d scan more part.
creating library of parts.
so we done with the first photoshoot session we got something off 150-200 pics
we started by just throwing it all to the software and letting at run the first stages, if more photos need then we can just grab the camera and go take more.
the camera i use nikon coolpix p100
but you can use any camera or phone
we run the software until the Structure from Motion stage
we run into problems with MeshRoom and cuda cores (Nvidia GPU). mesh room said to be using gpu to optimize part of the process (some task are better done with GPU). but when we run the software we found that only the cpu run. we dug into it.
solution: GPU is part of the pc that take jobs that need processing, in long story short, if you don't the gpu you want him to join the fight is just sitting there.
so we went to the Nvidia control panel and change it to include MeshRoom in the softwares list of the gpu
as you can see even though we took 109 pic we missed a spot, this calls for taking the camera and going to shoot even more in the missing area.
the process is easy as just putting more pic into the project and running the process again. the only diffrent now you have 2 branch the old computation and the new combining.
so the top line is the old and the bottom one is the new pipeline.
and thx for the GPU fix we done, the old branch and the fix only being 60 pics the process run way faster.
by the look of things because of the dark area of the shadow i couldn't get the fix to fill the missing hole. but we might try to fix it in the postprocess. it should be all good cause its not a complex part to model and fix.
the green square is the area of the problem. the shadows was so dark compere to the other parts and picture that the software could not find matching features between the pictures.
the red square is floating points left from mismatching of the feature matching. i hope the cleanup will fix this and would not create artifact.
the 3D scan in the MeshRoom. the more dark the more tringles and vertices and better accuracy
the black/gray area is the mash having a lot of detail, a lot of tringles. which is good.
now e do the same for the other side of the car the side that missing the part.
then we match the parts clean them and go for the next step.
after having the 2 parts in post process in right size and and good optimization, we are pass the hard part of the project and its smooth ride.
the 3d scan of the left side in Blender
the same part in blender. cant believe how easy it is. just drag and drop.
the second model was easy as the first, with same amount of problems. we needed to take some more photos. but it worked like a charm the most important think is to see if the holes as bean detected by the software
2 off the models in blender with texturing
the model is out with a lot of holes and tears, and needing fix.
i researched a little bit and found meshleb
free software to do exactly this
so in meshlab i clean and fix what i can throw it back to blender for more fix
ill tell you all the steps later
then upload it to onshape
onshape doesn't like the obj type and really doesn't like the scans, causing me more pain
after uploading the model with better topology, its time to make some cad.
i will say that for the next project what we going to do is just better and longer scanning.
this will solve a lot of problems like holes and large imperfections
for a start we need to align the models with right accuracy and measurement
one model give as the shape we want
end second model give us the holes placement
after this we get fully cade model for printing
While putting my own project aside for a while because I'm busy with college, I ended up helping my uncle to scan for his project (which I'll share here too). He faced a problem with the software:
[08:10:14.567179][info] Max number of threads regarding memory usage: 22
[08:10:14.567179][info] # threads for extraction: 22
This is his error code.
The code indicates something to do with threads in his laptop, which is surprising because his laptop has a CPU that is better suited for handling workloads. But when I was researching it and doing the scan for him, I discovered that Meshroom really needs a lot of details about the camera and camera sensor (which are sometimes saved as part of the image file). If Meshroom recognizes these details, then it's all good, but if you use some niche camera or phone, it can cause problems. A lot of calculations for feature meshing and depth mapping are done by also having the focal length, which helps calculate the estimated distance from the sensor to the object.
I'll have an entire post dedicated to problems in Meshroom and how to fix them, and also a bit of insight into 3D scanning and 3D in general.
aluminum